Description

Fixes #5918

The PORT value in js/widgets/reflection.js was hardcoded to a specific AWS IP address (http://3.105.177.138:8000), causing two problems:

1. Mixed-content security error on production: musicblocks.sugarlabs.org is served over HTTPS, so loading a http:// resource from a raw AWS IP is blocked by the browser. The widget silently fails for all production users.
2. Broken local development: Developers must manually edit the source file to change the URL, with no environment detection.

Changes Made

Replaced the hardcoded IP in js/widgets/reflection.js (init() method) with the same dynamic hostname-based resolver that aidebugger.js already uses:

this.PORT = (() => {
    if (
        window.location.hostname === "localhost" ||
        window.location.hostname === "127.0.0.1"
    ) {
        return "http://localhost:8000";
    } else if (
        window.location.hostname.includes("musicblocks.sugarlabs.org")
    ) {
        return `${window.location.protocol}//api.musicblocks.sugarlabs.org`;
    } else {
        return `${window.location.protocol}//${window.location.hostname}:8000`;
    }
})();

Testing

• On localhost: resolves to http://localhost:8000 ✅
• On musicblocks.sugarlabs.org: resolves to https://api.musicblocks.sugarlabs.org ✅
• On any other host: uses protocol//hostname:8000 ✅

Checklist

• I have read and followed the project's code of conduct.
• The change is consistent with the existing codebase (aidebugger.js uses the identical pattern).
• No tests needed — this is a configuration/URL resolution change with no logic side effects.